Posted by Jeff C from fw1.cybersafe.com (192.156.168.6)on March 06, 1998 at 20:45:11:
In Reply to: Big RRed posted by Chris Lundie on March 06, 1998 at 20:12:33:
>Visual C++
>First of all, if anyone can help with making Big RRed work under Visual C++ that would be great. Some people have told me it doesn't work right. I think the
>functions are being exported with the wrong names. For example, grGlideInit should be exported as _grGlideInit@0 but I think it's not working right.
This is correct. i finally got around to porting it last night to VC++, and I had to change all those damn things in the .def file.
MSVC++ exports whatever is in the .def file, it doesn't try very hard to compare what is actually in the file with what is being exported.
(actually it does, but how it does it is strange.)
I went through last night and also put in a new DLLMain that looks more Microsoft (it doesn't do anything different, it just has stubs
for initing and sutting down the DLL)
I also added a:
#ifdef _MSC_VER
#define __MSC__
#endif
so that the stupid, stupid GLIDE headers would realize that we were using MSC. This way, you do not have to modify the
glide header files (bad)
Before I did anything else major, I wanted to see if anyone had updated any source code. I don't want to clobber anyone
else's work.
If we have >1 person working on this, we should really give someone the responisibility of maintaining the codebase.
Everybody would send diffs bak and forth. I know windiff can be used to visually diff files, and I know that the GNU-WIN32
compiler comes with a command line diff, so we should be able to maintain this thing if one person decides to maintain the
code.
So one thing:
has the source changed for version .4? if it has, I can fold it into my VC++ built file. If no one else wants to maintain
this, I can. I have all the tools available to me both at home and on my home computer.